Skip to content

Attempt to use reflink on Windows#18118

Draft
zanieb wants to merge 3 commits intomainfrom
zb/windows-reflink
Draft

Attempt to use reflink on Windows#18118
zanieb wants to merge 3 commits intomainfrom
zb/windows-reflink

Conversation

@zanieb
Copy link
Copy Markdown
Member

@zanieb zanieb commented Feb 20, 2026

Extends #18117

ReFS and Dev Drives support reflinks on Windows

@zanieb zanieb force-pushed the zb/windows-reflink branch from a9e8aaf to b5098b7 Compare February 23, 2026 14:03
zanieb added 3 commits March 13, 2026 15:22
On Windows, `D:` without a trailing backslash is a relative path
meaning 'current directory on drive D', not the drive root. This caused
tempdirs to be created inside `D:\uv` (the repo), where uv discovers
`.python-versions` and requests Python 3.14.0.
Move the Windows copy-on-write default from unconditional to gated behind
the `reflink-windows` preview feature flag. On Windows, the default link
mode remains `Hardlink` unless the user opts in via `--preview-feature
reflink-windows` or `--preview`.

When the preview flag is enabled, the effective link mode is overridden
from `Hardlink` to `Clone` at each command entry point, so that
copy-on-write is attempted on ReFS/Dev Drive volumes.
@zanieb zanieb force-pushed the zb/windows-reflink branch from b5098b7 to b09d386 Compare March 13, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant